This PR integrates automated testing into the release workflow to ensure code quality before creating and publishing NuGet packages.

Changes Made

Added a test step to the build-all-configs job in .github/workflows/release.yaml that runs between the build and pack operations:

- name: Test
  run: dotnet test --no-build --configuration ${{ matrix.configuration }} --framework net9.0

Impact

The release workflow now follows this sequence:

1. Build - Compile code on all platforms (ubuntu, windows, macos) and configurations (Debug, Release)
2. Test - Run all 247 tests to validate functionality ⬅️ NEW
3. Pack - Create NuGet packages only if tests pass

This ensures that:

• Only thoroughly tested code gets packaged and published to NuGet.org
• Test failures will block the release process, preventing broken packages from being published
• The existing dependency chain (build-package depends on build-all-configs) means failed tests will halt the entire release pipeline

The test command uses --no-build for efficiency since the code was just built, and --framework net9.0 to ensure compatibility with the CI environment.

Fixes #122.

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.